5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

DATE ADD


The DATE ADD statement adds (or subtracts by adding a negative value) a number of time units (years, months, days) to a specified date/time field, to determine a future (or past) date/time. For example, you may want to add 10 days to the DUE DATE field to determine when a 10-day discount period for prompt payment expires.

  ?????   DATE ADD   ??? ?????????????????????? ??? ? ??? ?????????????????????? ???
  (1)                (2) (3)                    (4)(5)(6) (7)                    (8)

(1) T/F execution conditions
(2) Destination application ID
(3) Destination field name or PDF
(4) Destination occ (constant/index)
(5) Unit (8:centuries, 7:years, 6:months, 5:days, 4:hours, 3:minutes, 2:seconds, 1:hundredths)
(6) Source application ID
(7) Source field name, PDF, or constant
(8) Source occurrence (constant/index)

Using the Statement

The unit (parameter 5) indicates the units of the source field. The result is returned in the destination field.

When you add 'months' to a date, the destination 'day' does not change unless the resulting date is beyond the end of the month. In other words, if you add one month to February 28, you get March 28; however, if you add one month to January 31, you get February 28 (except in leap years, when you get February 29). When you add 'years' to a date, the destination month and day do not change, even in leap years.

Restrictions

The destination field must be a date/time field type and the source field must be a numeric field type. Also, results can be unpredictable if you are using a date field without a century component. Confirm that your System Administrator has set up the Pivot Year environment variable to avoid unexpected results.

Execution Error

If the destination field is null, a runtime error occurs.

Related Statements

DATE BTW

Example

The following example calculates a discount date 10 days in the future and displays it on an image:

          SET      TAR WORK DISCOUNT DATE             =  TAR INVOICE DUE DATE
          DATE ADD TAR WORK DISCOUNT DATE         5      10
          DISPLAY  TAR WORK DISCOUNT DATE         (AT APPEARANCE #    )

Note that the INVOICE DUE DATE field is moved into a work field called DISCOUNT DATE before the computation is performed so that the INVOICE DUE DATE field is not modified.

Application Design Manual                                         "Powered by Appx Software"

635

©2006 By APPX Software, Inc. All Rights Reserved